Welcome![Sign In][Sign Up]
Location:
Search - linux m

Search list

[Linux-Unixglibc-2.3.2.tar

Description: Glibc 2.3.2源代码(解压后有100多M),相当珍贵的Linux资料-Glibc offers 2.3.2 source code (decompression after more than 100 M), very valuable information on Linux
Platform: | Size: 18115189 | Author: 华科大 | Hits:

[Algorithmhyplas

Description: ************************************************************************ * * * * * THIS IS THE H Y P L A S 2.0 README FILE * * ----------------- * * * * HYPLAS is a finite element program for implicit small and large * * strain analisys of hyperelastic and elasto-plastic two-dimensional * * and axisymmetric solids * * * * HYPLAS v2.0 is the companion software to the textbook: * * EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for * * Plasticity: Theory and Applications. Wiley, Chichester, 2008. * * (www.wiley.com/go/desouzaneto) * * * * Copyright (c) 1998-2008 EA de Souza Neto, D Peric, D.R.J. Owen * *----------------------------------------------------------------------* * File last updated: 18 October 2008 * * * * This file belongs in the directory ../HYPLAS_v2.0 * ************************************************************************ * * * I M P O R T A N T * * * * READ SECTIONS 0 TO 3 OF THIS FILE CAREFULLY BEFORE ATTEMPTING * * TO COMPILE AND RUN THE PROGRAM HYPLAS ON YOUR COMPUTER !! * * * * THE AUTHORS DO NOT GUARANTEE THAT ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN IN THIS README FILE WILL WORK ON ANY PARTICULAR OPERATING * * SYSTEM. IF YOU DECIDE TO FOLLOW ANY SUGGESTIONS/INSTRUCTIONS * * GIVEN HERE YOU MUST DO SO AT YOUR OWN RISK. * * * * * * BUG REPORTS: Please send bug reports to * * * * hyplas_v2.0@live.co.uk * * * * Messages sent to the authors' personal email addresses * * will NOT be answered. * ************************************************************************ This file contains the following sections: 0. Copyright statement and disclaimer 0.(a) Copyright statement 0.(b) Disclaimer 0.(c) Conditions of use 1. Introduction 1.(a) Note on portability 2. Compiling and running HYPLAS 2.(a) Memory requirements 2.(b) Testing a newly compiled executable 3. The HYPLAS directory tree 4. Cross-referencing between the source code and the textbook 5. HYPLAS error messaging 6. Further remarks on HYPLAS ************************************************************************ 0. COPYRIGHT STATEMENT AND DISCLAIMER ================================== 0.(a) Copyright statement ------------------- You may only use this program for your own private purposes. You are not allowed, in any circumstances, to distribute this program (including its source code, executable and any other files related to it, either in their original version or any modifications introduced by you, the authors or any other party) in whole or in part, either freely or otherwise, in any medium, without the prior written consent of the copyright holders. 0.(b) Disclaimer ---------- This program (including its source code, executable and any other files related to it) is provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, any implied warranties of fitness for purpose. In particular, THIS PROGRAM IS BY NO MEANS GUARANTEED TO BE FREE FROM ERRORS. This program (or any modification incorporated to it by you, the authors or any other party) will run entirely at your risk. The results produced by this program are in no way guaranteed to be fit for any purpose. Under no circumstances will the authors/copyright holders be liable to anyone for damages, including any general, special, incidental or consequential damages arising from the use or inability to use the program (including, but not limited to, loss or corruption of data, failure of the program to operate in any particular way as well as damages arising from the use of any results produced by the program for any purpose). 0.(c) Conditions of use ----------------- You may only use this program if you fully understand and agree with the terms of the above disclaimer. You must not use this program if you do not agree with or do not understand (fully or in part) these conditions of use. 1. INTRODUCTION ============ HYPLAS is a finite element code for small and large strain analysis of hyperelastic and elasto-plastic solids. Most procedures implemented in HYPLAS are described in detail in its companion textbook: EA de Souza Neto, D Peric & DRJ Owen. Computational Methods for Plasticity: Theory and Applications. Wiley, Chichester, 2008 (www.wiley.com/go/desouzaneto). 1.(a) Note on Portability ------------------- HYPLAS has been written in standard ANSI FORTRAN 77. Currently, the only known (and deliberate) exceptions to the FORTRAN 77 ANSI standard are the instructions: INCLUDE '' used in many routines to include the HYPLAS database files (common blocks and global variables), and; CALL GETENV('HYPLASHOME',HYPLASHOME) used in subroutine "ERRPRT" (file ../HYPLAS_v2.0/src/GENERAL/errprt.f). This instruction inquires the name of the system environment variable HYPLASHOME and writes it on the character string HYPLASHOME. This instruction is NOT part of the ANSI FORTRAN 77 standard, but seems to work in most currently available FORTRAN 77 compilers. 2. COMPILING AND RUNNING H Y P L A S ================================== The HYPLAS source code is stored in directory ../HYPLAS_v2.0/src/ (../HYPLAS_v2.0/ being the current directory) and all its subdirectories. To generate an executable file, you just need to compile the FORTRAN source files: ../HYPLAS_v2.0/src/hyplas.f and ../HYPLAS_v2.0/src/*/*.f together. We recommend that the executable HYPLAS be stored in the directory ../HYPLAS_v2.0/bin to which the environment variable HYPLASHOME should be set (see below how to set a system environmental variable). WINDOWS (R) systems ------------------- On Microsoft Windows(R) systems, HYPLAS has been successfully compiled using Intel Visual Fortran Compiler(R) integrated with Microsoft Visual Studio(R). Here you only need to create a project that contains all Fortran source files mentioned above as well as the include files ..\HYPLAS_v2.0\src\*.INC On a Windows XP system, the system environment variable HYPLASHOME can be set as follows: 1. Open a File Manager 2. Right-click on the "My Computer" icon 3. Select "Properties" on the drop-down menu 4. A new window named "System Properties" will pop-up. Here select the "Advanced" tab. 5. On the "Advanced" tab, click the "Environment Variables" button. 6. A new window titled "Environment Variables" will pop-up. Here click the button "New" in the "System Variables" section of the window. 7. A new window will pop-up titled "New System Variable". Here you should fill the fields "Variable name" and "Variable Value", respectively, with HYPLASHOME and the path name (in full) of the directory ..\HYPLAS_v2.0\bin. 8. Press "OK" on the relevant pop-up windows. 9. The next time the computer is REBOOTED, this variable will be set to the correct path and HYPLAS should be able to find the error messages file ERROR.RUN if required. UNIX/LINUX systems ------------------ In a UNIX/LINUX operating system using a C-shell, for instance, the HYPLASHOME environment variable should be set with the command: setenv HYPLASHOME where here denotes the full path to the directory ../HYPLAS_v2.0/bin. To compile HYPLAS (from directory ../HYPLAS_v2.0/src) with a FORTRAN 77 compiler such as g77, you can use the command: g77 -o ../bin/hyplas hyplas.f */*.f Note that the executable file "hyplas" will be stored in the directory ../HYPLAS_2.0/bin (i.e. the directory set in the HYPLASHOME environment variable). Alternatively, you may use the Makefile provided (with suitable modifications, if needed) to create the HYPLAS executable. IMPORTANT: Before generating a HYPLAS executable, read Sections 2.(a) and 2.(b) below. 2.(a) Memory Requirements ------------------- HYPLAS memory requirements depend on the array dimensioning parameters set in files: ../HYPLAS_v2.0/src/ ELEMENTS.INC GLBDBASE.INC MATERIAL.INC MAXDIM.INC Files ELEMENTS.INC, GLBDBASE.INC and MATERIAL.INC contain parameters which are associated with the currently implemented finite elements and materials. DO NOT MODIFY THEM ! unless you are absolutely sure of what you are doing (only developers coding new elements or new material models/analysis types may need to modify them by changing the existing dimensioning parameters and/or including new parameters). The ONLY dimensioning file that can be safely modified by the average user is the file MAXDIM.INC This file contains the array dimensioning parameters related to the maximum permissible dimension of problems to be analysed by HYPLAS. These parameters include the maximum number of nodes, elements, element groups, etc. If necessary, CHANGE THESE PARAMETERS TO SUIT YOUR PROBLEM SIZE/MEMORY REQUIREMENTS before compiling HYPLAS. 2.(b) Testing a newly compiled executable ----------------------------------- After you have successfully compiled the HYPLAS source code and created an executable file, the next step is to run some tests to verify that HYPLAS is working well. To do this, proceed as follows: The directory ../HYPLAS_v2.0/book_examples/data_files contains a series of data files named .dat of benchmarked examples described in the companion textbook. The corresponding (benchmarked) result files are in the directory ../HYPLAS_v2.0/book_examples/result_files This directory contains a series of result files named .res generated with the current version of HYPLAS on a tested platform. All these files have been named such that their names start with the textbook section number where the corresponding example is described. For instance, files 14_9_2_tresca.dat and 14_9_2_tresca.res refer to a problem described in section 14.9.2 of the textbook, and so on. To check that HYPLAS is working well on your platform, after compiling HYPLAS, run the program HYPLAS for the examples of files .dat and compare the newly generated results .res with their benchmarked counterparts (of the same filename) in the result_files directory. To run an example, execute HYPLAS and use the keyboard to enter the name of the corresponding data file in full (including the extension .dat). To compare the benchmarked .res files against their newly generated you may proceed as follows: 1. On MICROSOFT WINDOWS systems - Here we have successfully used the software "ExamDiff" (the task was made particularly easy by selecting "View" and then the "Show Differences Only" option - this refers to version 1.8 of this software). 2. On UNIX/LINUX systems - Here we use the "diff" command from a shell window (and set the option to ignore blank spaces). A shell script may be used to perform this task automatically (including running HYPLAS and checking for result file differences) for all benchmarked examples provided. IMPORTANT: THE ONLY ACCEPTABLE DIFFERENCES BETWEEN A THE NEWLY GENERATED RESULT FILES AND THEIR BENCHMARKED COUNTERPARTS ARE THE DIMENSIONING PARAMETERS (FROM FILE MAXDIM.INC) USED TO COMPILE THE NEW EXECUTABLE (THESE PARAMETERS ARE PRINTED RIGHT AT THE BEGINNING OF THE RESULT FILES) AND NUMERICAL DIFFERENCES IN RESULTS DUE TO NUMERICAL "ROUNDING-OFF" (THESE ARE VERY SMALL DIFFERENCES THAT DEPEND ON THE PRECISION OF ARITHMETIC OPERATIONS IN THE PLATFORM USED). ALSO NOTE THAT THE EXAMPLES OF THE COMPANION TEXTBOOK DO NOT COVER ALL FEATURES OF HYPLAS. HENCE THIS TEST DOES NOT GUARANTEE THAT EVERYTHING IS WORKING PROPERLY. 3. THE H Y P L A S DIRECTORY TREE ================================ 3.(a) Summary ------- ../ HYPLAS_v2.0/ bin/ book_examples/ data_files/ result_files/ man/ html/ src/ CRYSTAL/ DAMAGE/ DAMAGED_ELASTIC/ DRUCKER_PRAGER/ ELASTIC/ ELEMENTS/ GENERAL/ MATERIALS/ MATHS/ MOHR_COULOMB/ OGDEN/ TRESCA/ VON_MISES/ VON_MISES_MIXED/ 3.(b) Description ----------- The HYPLAS program directory tree is organised as follows: ../HYPLAS_v2.0/ (this directory) This is the HYPLAS root directory, where the HYPLAS directory tree starts. ../HYPLAS_v2.0/bin/ This directory contains the file ERROR.RUN where most HYPLAS error/warning messages are. IMPORTANT: the environment variable HYPLASHOME should be set to this directory. Otherwise, HYPLAS will not find its error/warning messages when required. We also recommend that the EXECUTABLE of HYPLAS be stored in this directory. ../HYPLAS_v2.0/book_examples/ This directory has the following subdirectories: ../HYPLAS_v2.0/book_examples/data_files ../HYPLAS_v2.0/book_examples/result_files Refer to Section 2.(b) above for further details. ../HYPLAS_v2.0/man/ This is the HYPLAS documentation/manuals directory. It contains the following files: input_man.txt - A concise input data manual for HYPLAS in ASCII format; hyplas_calltree.txt - Contains a flowgraph (shows the call tree) of HYPLAS in ASCII-format. Note: calls to function subprograms are not included in this flowgraph; and the subdirectory: ../HYPLAS_v2.0/man/html This directory contains the hypertext (HTML) format Fortran source code and of manual pages of the entire HYPLAS program. Manual pages with descriptions of each function/subprogram including their argument list are linked to their corresponding HTML-format source code. This allows the user the navigate through the HYPLAS source code using a web browser. To start at the main program, use your web browser to open the file hyplas.html. This facility should be helpful to those trying to understand the flow of program HYPLAS. ../HYPLAS_v2.0/src/ This directory (and its subdirectories) contains the Fortran source code of HYPLAS. The files containing the sources are named following the standard practice: .f where is the name of the FORTRAN procedure (subroutine, function subprogram, etc.) whose source code is in file .f. The source code of the HYPLAS main program is in file hyplas.f and the HYPLAS database (COMMON blocks, array dimensioning parameters and other global parameters) is coded in the "include files" ELEMENTS.INC GLDBASE.INC MATERIAL.INC MAXDIM.INC in this directory. In addition, this directory contains a file named "Makefile" (UNIX-LINUX Release only) which may be used for compiling and linking HYPLAS in UNIX/LINUX systems. The subdirectories of ../HYPLAS_v2.0/src are as follows: ../HYPLAS_v2.0/src/CRYSTAL Contains the source code of all procedures related to the finite strain single crystal plasticity model implemented in HYPLAS. ../HYPLAS_v2.0/src/DAMAGE Source files of the procedures related to the Lemaitre ductile damage model implementation. ../HYPLAS_v2.0/src/DAMAGED_ELASTIC Source files of the procedures related to the damaged elasticity model with crack closure effect. ../HYPLAS_v2.0/src/DRUCKER_PRAGER Source files of the procedures related to the implemented Drucker-Prager plasticity model. ../HYPLAS_v2.0/src/ELASTIC Source files of the procedures related to the linear elasticity model (Hencky model under large strains) implemented. ../HYPLAS_v2.0/src/ELEMENTS Source files of the element interfaces and element-related procedures. ../HYPLAS_v2.0/src/GENERAL Source files of general procedures. ../HYPLAS_v2.0/src/MATERIALS Source files of the material interfaces. ../HYPLAS_v2.0/src/MATHS Source files of the mathematical procedures. ../HYPLAS_v2.0/src/MOHR_COULOMB Source files of the procedures related to the implemented Mohr-Coulomb plasticity model. ../HYPLAS_v2.0/src/OGDEN Source files of the procedures related to the implemented Ogden hyperelasticity model. ../HYPLAS_v2.0/src/TRESCA Source files of the procedures related to the implemented Tresca plasticity model. ../HYPLAS_v2.0/src/VON_MISES Source files of the procedures related to the implemented von Mises plasticity model with isotropic hardening. ../HYPLAS_v2.0/src/VON_MISES_MIXED Source files of the procedures related to the implemented von Mises plasticity model with mixed isotropic/kinematic hardening. 4. CROSS-REFERENCING BETWEEN THE SOURCE CODE AND THE TEXTBOOK ========================================================== Many references are made in the textbook to various subprograms of HYPLAS. These are usually made when a particular procedure described in the text is implemented in the program. The reader should refer to the textbook index. Also, a substantial number of comment lines have been added to the source code of HYPLAS with reference to sections, figures, boxes, etc of the textbook related to the part of the code in question. Such references are usually displayed after the word "REFERENCE:" (in capitals) on commented lines. Searching for this word will take you to the line of code where the particular routine has a reference to the textbook. NOTE: Occasional references to other textbooks/journal papers are also made following the word "REFERENCE:" on commented lines. 5. HYPLAS ERROR MESSAGING ====================== Most error/warning messages issued by HYPLAS are in the ASCII-format file ERROR.RUN (kept in the HYPLASHOME directory - ../HYPLAS_v2.0/bin). All such error/warning messages have an identification code (e.g. ED0015) which is printed both to the standard output (this is usually the computer screen) and to the relevant results file. If you wish to find where in the source code a particular message is being issued, then perform a search for the corresponding message identification code in the entire source code of HYPLAS. 6. FURTHER REMARKS ON HYPLAS ========================= 6.(a) Program efficiency THIS SECTION IS OF INTEREST ONLY TO THOSE WANTING TO MAKE HYPLAS RUN FASTER. It is particularly stressed in the textbook that this program has not been designed having efficiency in mind (refer to Section 5.1.2 of the textbook). Its structure has been designed mainly to illustrate in a relatively clear manner the computer implementation of the techniques and algorithms described in the text, with a particular view to the implementation of solid constitutive models and finite elements. For those who are especially interested in the speed of the code, there are a few tips that could help in this direction. Unfortunately, these involve modifications to the source code which is probably most appropriate to readers with a good level of experience in finite element programming. To those with this particular interest, we can suggest the following: (i) The use of faster linear solvers This is probably the change that would result in a greater gain in efficiency. The Frontal Method adopted in subroutine FRONT (file ../HYPLAS_v2.0/src/GENERAL/front.f) has been designed originally to save memory (back in the days when computer memory was severely limited). There are currently a vast number of methodologies which focus on speeding up the linear solution, in addition to reducing memory storage requirements (which is a particularly important issue in the solution of large scale problems). Some of these are extensions/refinements of the original Frontal solver. We remark that a number of such procedures (with their respective source codes) are available (conditions may apply) from the LAPACK (Linear Algebra PACKage - http://www.netlib.org/lapack) repository or from the HSL Library (http://www.cse.cse.scitech.ac.uk/nag/hsl). For the reader interested in gaining speed, we would recommend the replacement of the existing solver of FRONT by a faster one. We remark though that this is a substantial programming task. Another aspect here is the fact that computing times in FRONT are directly linked to the frontwidth of the system which, in the present version of HYPLAS is fixed and depends, for a given mesh, on how the degrees of freedom are numbered (node numbering). The incorporation of a frontwidth optimiser (which re-numbers the degrees of freedom in order to minimise the frontwidth) in FRONT could produce some good savings in computing times. Such savings become particularly noticeable in larger problems where the original node numbering produces an excessively large frontwidth. (ii) Material-specific computations The issues pointed out here affect only the computing times for specific material models and are expected to have a much lower impact in overall speed than the linear solver issue discussed above. Some of the material model-specific computations carried out in HYPLAS could be made a bit faster. For example, for isotropic models whose stress update is carried out in the principal stress space (such as the Tresca and Mohr-Coulomb models - see routines SUTR and SUMC, files ../HYPLAS_v2.0/src/TRESCA/sutr.f and ../HYPLAS_v2.0/MOHR_COULOMB/sumc.f, respectively) the spectral decomposition of the stress in carried out in the state update update routine and then repeated in the corresponding routine for computation of the consistent tangent operator (refer to files ../HYPLAS_v2.0/src/TRESCA/cttr.f and ../HYPLAS_v2.0/src/MOHR_COULOMB/ctmc.f, respectively, for the Tresca and Mohr-Coulomb plasticity models). Some savings in computing time can be achieved here by storing the stress eigenprojection tensors (these can be stored as state variables) during the execution of the state updating and then retrieving them later for use in the computation of the consistent tangent operator. This change can be incorporated to the code relatively easily. The computation of the exponential map and is derivative for the single crystal plasticity model (routines EXPMAP, file ../HYPLAS_v2.0/src/CRYSTAL/expmap.f and DEXPMP, file ../HYPLAS_v2.0/src/CRYSTAL/dexpmp.f) is carried out in three dimensions (these routines have been adapted from an earlier three-dimensional code). To improve efficiency, these can be adapted to work only in two-dimensional problems by removing the unnecessary operations related to the third dimension. 6.(b) Output of nodal averaged values The reader should be aware that the way in which nodal averaged values of stresses and other variables are calculated in HYPLAS is very basic (and rudimentary). This feature of the program is made available only to help those interested in producing contour plots, etc from results presented in HYPLAS result files and should be useful in many circumstances of interest. This facility has in fact been used in producing many of the figures presented in the textbook. But note, for example, that the values of incremental plastic multipliers for plasticity models may take (inadmissible) negative values when extrapolated from Gauss-point to nodes and averaged. We remark that more sophisticated and refined techniques of transferring Gauss point values of variables to nodal points and obtaining the corresponding smoothed field are available in the current literature. These fall outside the scope of the companion textbook of HYPLAS.
Platform: | Size: 11008084 | Author: gtcewli3 | Hits:

[SMSsmslink-0.44b.tar

Description: ~{JV;z6LO{O"7~Nq5D7~NqFw:M?M; 6K~}(linux~{#)~}
Platform: | Size: 93184 | Author: ~{B^:#G?~} | Hits:

[Embeded Linuxmp3play

Description: uclinux下s3c4510B CPU播放mp3 C程序-Basis under s3c4510B CPU mp3 player C Program
Platform: | Size: 224256 | Author: 曾式 | Hits:

[Communicationrp-pppoe-3.4.tar

Description: 0. Install the rp-pppoe-software -------------------------------- You should have already done this by the time you re reading this. If not, go back and read README. 1. Set up your Ethernet hardware -------------------------------- First, make sure the Ethernet card you intend to use with the modem is visible to the Linux kernel. Just how to do this is beyond the scope of this document. However, if the card is the only Ethernet card in the system, executing: ifconfig eth0 should display something like this: eth0 Link encap:Ethernet HWaddr 00:60:67:62:31:D4 plust some more lines. Your HWaddr will be different. As long as you see the HWaddr line, your card should be working. DO NOT assign an IP address to the Ethernet card. DO NOT configure the card to come up at boot time.-0. Install the rp- PPPOE-software-------------------------------- You should have al ready done this by the time you re reading this. I f not, go back and read README. 1. Set up your Ethernet h ardware-------------------------------- F irst, make sure the Ethernet card you intend to use wit h the modem is visible to the Linux kernel. Just h ow to do this is beyond the scope of this document . However, if the card is the only Ethernet card in the Syste m, executing : ifconfig eth0 should display something like th is : eth0 Link encap : Ethernet HWaddr 00:60:67:62 : 31 : D4 plust some more lines. Your HWaddr will be dif peptide. As long as you see the HWaddr line, your card should be working. DO NOT assign an IP a http://www.hotmail.com/ to the Ethernet card. DO NOT configure th e card t
Platform: | Size: 187392 | Author: chensi | Hits:

[MPIRPC_SDKWindowsVersion_oncrpc

Description: 这个是Windows版本,不是Linux版本 Netbula RPC for Win32 supports multithreading, this document describe the procedure to build multithreaded (MT) RPC server and clients-this is the Windows version, not Netbula RPC Linux version supports multi for Win32 threading. this document describe the procedure to build m ultithreaded (MT) RPC server and clients
Platform: | Size: 456704 | Author: infinite8 | Hits:

[OtherJOVE416S.ZIP

Description: JOVE is Jonathan s Own Version of Emacs. It is based on the original EMACS editor written at MIT by Richard Stallman. Although JOVE is meant to be compatible with EMACS, there are some major differences between the two editors and you shouldn t rely on their behaving identically. -JOVE is Jonathan's Own Version of Emacs. It i 's based on the original EMACS editor written at M IT by Richard Stallman. Although JOVE is meant t o be compatible with Linux, there are some major differences between the tw o editors and you should not rely on their behavin g identically.
Platform: | Size: 462848 | Author: 郭春阳 | Hits:

[Embeded LinuxUSB_CDC_ACM_DRIVER

Description: USB Abstract Control Model driver for USB modems and ISDN adapters(for Linux)-USB Abstract Control Model driver for USB m odems and ISDN adapters (for Linux)
Platform: | Size: 9216 | Author: 陶昱良 | Hits:

[Otherhulmsg_client_200608

Description: Hulft-Message是用来在Internet上传输文件数据的商用MiddleWare,特别用于数据量小,但是频繁度高的业务。支持不同平台和编码体系间的代码和数据的自动识别和转换。 本代码是Hulf-Message的Client的源代码和lib库,平台包括LINUX/UNIX/OS400/Windows,功能包括和Server端建立连接,发送和取得数据功能,语言包括C语言和JAVA语言。-Hulft- Message is used for the transmission of documents on the Internet data business M iddleWare, especially for a small amount of data, but the frequent high-level business. Support of different platforms and the coding system code and data conversion and automatic identification. The code is Hulf-Client Message of the source code and the lib, LINUX/UNIX/OS400/Windows platform including, Server features include terminal and connect, send and access to data functions, languages including C language and JAVA.
Platform: | Size: 2793472 | Author: yuxg | Hits:

[OS DevelopExe2Img

Description: 这个文件最初在一个m-ix86pm的UCOS For 386包中, 但是没有源代码,原名叫ExeToImg.EXE 用于将PE结构的EXE文件转换为内存映像文件, 可用于在WIN平台上开发基于x86的操作系统 这个源代码编译后效果跟原版差不多,是我用OllyDBG反编译写成C的. 对于学习PE文件及操作系统有一定作用, 毕竟我的大部分的操作是在window下, 机器差得要得,不想用虚拟机在linux下编译入门的操作系统. 像<自己动手写操作系统>中的Tinux -This document was originally in a m-ix86pm the UCOS For 386 package, but no source code, the original name used to ExeToImg.EXE structure of PE files into memory EXE image file that can be used in the WIN platform x86-based operating system of the source code compiled with the original effect is almost that I wrote with OllyDBG decompile C
Platform: | Size: 20480 | Author: tary | Hits:

[Linux-UnixMP3_Decoder_Evaluation_Version_2.0.6

Description: mp3 源码。支持8Kbps~320KBps MP3文件。ADI DSP-mp3 source. Support 8Kbps ~ 320KBps MP3 files. ADI DSP
Platform: | Size: 6609920 | Author: personal11 | Hits:

[Embeded LinuxMatrix500

Description: The source code example of ARM9 development board from Artila (M-501 starter kit). The source code can compile on linux or cygwin. find more information on http://www.artila.com/p_matrix.html#m_501.-The source code example of ARM9 development board from Artila (M-501 starter kit). The source code can compile on linux or cygwin. Find more information onhttp:// www.artila.com/p_matrix.html#m_501.
Platform: | Size: 340992 | Author: Jitkasem | Hits:

[Delphi VCLmtdorb

Description: For build this project you can use ant (www.apache.org). Before build project rename file build.properties.pattern in build.properties and set specific for your machine parameters, then start build.bat (for Windows platform) or build.sh (for Linux) in root project folder. After compile process all binary files will be copy into build forlder. For additional information please visit web site http://www.m-g.ru/corba To subscribe on news about MT_DORB send e-mail with subject subscribe to corba@m-g.ru We recommend that you place the MTDORB_UCUtils.dll ( or MTDORB_UCUtils.so for Linux) in the Windows\System directory (or Windows\System32 for WinNT and Win2K and /lib for Linux). Main MTDORB author: Oleg V. Safonov <safonov@m-g.ru>
Platform: | Size: 4161536 | Author: SophiaLung | Hits:

[Audio programreal-time_LPC_analysis_synthesis_visualization_1.0

Description: rt_lpc is a light-weight application that performs real-time LPC analysis and synthesis. It features the following: real-time LPC analysis real-time LPC synthesis visualization of original, predicted, and error waveforms visualization of vocal tract shape from LPC coefficients adjustable LPC analysis order adjustable synthesis pitch shift MIDI controlled pitch (hit m ) lots of other choices (pitch pulse source selection, emphasis filter) STFT plot modular LPC library available on MacOS X, Linux, and Windows under GPL part of the sndtools distribution
Platform: | Size: 111616 | Author: 尉迟雪凝 | Hits:

[Linux-Unixpcsc-lite-1[1].4.102.tar.bz2

Description: linux 下的pcsc驱动 pcsclite 下载后更改m名字 去掉。zip后缀-pcsc drivers under linux after downloading pcsclite change m name removed. zip suffix
Platform: | Size: 460800 | Author: liyang | Hits:

[Driver Developromfs

Description: I want to provide an example file system driver for Windows NT/2000/XP. For some time I have worked on an implementation of RomFs. RomFs is a small filesystem originally implemented in Linux, because of its simple disk layout its a good choice for an example driver. The current status is a working read-only driver that supports caching of file data, the create functionallity still needs some work but I m releasing it due to the high public demand. -I want to provide an example file system driver for Windows NT/2000/XP. For some time I have worked on an implementation of RomFs. RomFs is a small filesystem originally implemented in Linux, because of its simple disk layout its a good choice for an example driver. The current status is a working read-only driver that supports caching of file data, the create functionallity still needs some work but I m releasing it due to the high public demand.
Platform: | Size: 835584 | Author: Showna | Hits:

[Streaming Mpeg4baseON_ARM_MPEG4.pdf

Description: 基于ARM的MPEG4视频解码器的优化。本文对嵌入式软件开发人员有参考价值,本人从事嵌入式多媒体软件开发。对MPEG4,ARM,MIPS有些研究,此文对基于ARM的MPEG4视频解码器优化为开发人员提供了新的思路。-ARM-based MPEG4 video decoder optimization. In this paper, embedded software developers have a reference value, I engaged in embedded multimedia software development. On MPEG4, ARM, MIPS, some research, this article based on ARM s MPEG4 video decoder optimized for the developers to provide a new way of thinking.
Platform: | Size: 228352 | Author: H Simon | Hits:

[Linux-Unixmconlinux.tar

Description: 在linux系统下开发研究移动通信的工具型代码,内附m序列 walsh函数等完整C程序,有很高的参考学习价值-Linux system in the research and development tool for mobile communications-based code, containing a sequence of walsh function m, such as a complete C program with a high degree of reference to learn the value
Platform: | Size: 73728 | Author: sea | Hits:

[Shell apiSudungLinuxShell

Description: 1. LỊ CH SỬ RA Đ Ờ I CỦ A LINUX Vào nă m 1991 tạ i Phầ n Lan, Linus B. Torvalds lúc đ ó là sinh viên ở trư ờ ng Đ ạ i họ c tổ ng hợ p Hensinki đ ã dùng mộ t máy tính cá nhâ n có trang bị bộ xử lí 386 đ ể nghiên cứ u cách làm việ c củ a nó . Do hệ đ iề u hành MS-DOS khô ng khai thác đ ầ y đ ủ các đ ặ c tính củ a bộ xử lí 386 , Linus đ ã sử dụ ng mộ t hệ đ iề u hành thư ơ ng mạ i khác là Minix . Hệ đ iề u hành Minix là hệ đ iề u hành Unix cỡ nhỏ -1. LỊ CH SỬ RA Đ Ờ I CỦ A LINUX Vào nă m 1991 tạ i Phầ n Lan, Linus B. Torvalds lúc đ ó là sinh viên ở trư ờ ng Đ ạ i họ c tổ ng hợ p Hensinki đ ã dùng mộ t máy tính cá nhâ n có trang bị bộ xử lí 386 đ ể nghiên cứ u cách làm việ c củ a nó . Do hệ đ iề u hành MS-DOS khô ng khai thác đ ầ y đ ủ các đ ặ c tính củ a bộ xử lí 386 , Linus đ ã sử dụ ng mộ t hệ đ iề u hành thư ơ ng mạ i khác là Minix . Hệ đ iề u hành Minix là hệ đ iề u hành Unix cỡ nhỏ
Platform: | Size: 281600 | Author: vu | Hits:

[Linux-Unixgdb

Description: 将g l i b函数库、G t k +构件库、G n o m e库和G C C编译器结合起来可以用来开发非常复杂的应 用程序,足以满足绝大多数的商业应用。但是这些还不足以成为一个完整的开发平台。还需 要一个高效的调试器,特别是对较大型的应用程序,这一点更为重要。-Linux 包含了一个叫g d b的G N U调试程序。gdb 可以用来调试使C、C++以及M o d u l a-2语 言开发的程序
Platform: | Size: 348160 | Author: 李智军 | Hits:
« 1 2 3 4 56 7 8 9 »

CodeBus www.codebus.net